Updated the branch to latest master (conflicts in documentation only)

Updated branch on top of latest v1.52.0 release

@aeschright any chance this gets reviewed and merged please

@radeksimko could this be reviewed and merged please ?

@bflad sorry to ask you directly for this but as I saw your work in issues 9345 and 9598 do you think this one could be merged too ? Many thanks in advance

Terraform team, any chance this can get reviewed soon please ?

@bflad @radeksimko @aeschright Is there any specific procedure/alias/... I should follow/write to in order to get this reviewed and potentially merged quite quickly? Many thanks in advance

Hi folks, I think customizable timeouts are one of the things that require some internal discussion before we can go ahead with them. As you probably noticed, we're working through a pretty big backlog of PRs, and some team members (like me!) are still quite new. Any info you can put on the associated issue #3128 about your use cases and existing workarounds will help us proceed. Thanks for your patience! We really appreciate the contribution.

@aeschright thanks for your answer and be sure I understand your point here. However there have been other cases like #51677, #3910, #3639 and #3599 (and may be others) that have made their ways into the code.
As I am taking over this PR from a former person in my company, I can not really give your more insight about why this was submitted and can not give more insight into associated issue #3128.
However, we would like to get rid of our own version of terraform-aws-provider where we have this code merged and use the standard official delivery once this gets merged
Many thanks for your understanding

Any progress on this one please @aeschright @bflad @ryndaniels ? Thanks

@aeschright @bflad @ryndaniels have you been able to discuss about this ?

@aeschright @bflad @ryndaniels any progress on this one please ?

@aeschright @bflad @ryndaniels any plans to make progress on this one soon please ?

@terraformteam

@aeschright @bflad @ryndaniels any chance this one gets addressed someday please ?

@terraformteam anything I can do to have this addressed soon ???

Any news on this please ?

@ewbankkit as you helped me out with lambda & timeout issues some time ago, may be you could pass this one on to people who might be willing to have a look at this please ? Many thanks in advance

@aeschright @bflad @ryndaniels @ewbankkit any chance this one gets addressed someday please ?

Any news ?

Could this be integrated/discussed/adressed somehow ?

Nothing new ? Can someone tell me how to make progress on this please ?

@obourdon the additional pings and comments, that do not add additional questions or relevant information to the initial description, do not change our prioritization of an issue or PR, but they do generate a lot of notification noise for us and any others subscribed or participating that slow down our response to items.

I understand your frustration with not knowing exactly when something will be delivered or a timeline, especially when its affecting your day to day work. Explaining your need like you did in one of your earlier comments is great and does help us better understand priorities. "+1", "Any news?" type comments though do not further the cause of an issue (reactions do though, as that is one signal we use in prioritization).

All that being said, I believe this issue is solved in #9812.

@paultyng many thanks for pointing this out and sorry for those many updates, however I thought this was a way to prevent the Hashibot from accidentally closing/downgrading the issue/PR due to inactivity and was hoping to at least get feedback or time estimates for feedback (may be I have taken those different habits whe I worked with/for the OpenStack community ;-) )

I agree that looking at the code integrated in #9812 might solve the issue but still does not allow users to configure the timeouts from within their HCL code so may be you could reopen this and potentially integrate it in a next release of the AWS provider.

Thanks for your understanding

@paultyng is there a way to reopen this PR please ? (see comment above)

Hi @obourdon 👋 If you are still having trouble with version 2.25.0 or later of the Terraform AWS Provider, which includes the fix from #9812 that should negate the need for this type of change, please submit a new GitHub bug report for further discussion about the behavior you are seeing including debug logs.

In general, customizable timeouts should not be required for Terraform AWS Provider resources except in cases where operation times are affected by some scalable dimension of the resource itself (e.g. database size affecting the length of time required for aws_db_instance resource update operations). We generally want to discourage customizable timeouts otherwise since the configuration option may not help the situation and instead be masking issues that should be fixed in the resource code for all operators, such as increasing an underlying default/hardcoded timeout.

@bflad thanks for this update. I now understand more your standpoint. We will see if we can reproduce the issue with latest versions of the provider

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!